feat(v2): auto-branch, fix-all resolve, README overhaul#169
Merged
Conversation
Three v2 polish improvements: 1. Auto-branch creation: implementation-orchestration now spawns Git agent setup-task on protected branches instead of asking users. Git agent detects repo branch naming conventions from existing remote branches before deriving names. 2. Fix-all resolve: resolver gains pragmatic validation (WONT_FIX for impractical fixes), systematic 6-step refactoring protocol for careful fixes, and narrowed deferral criteria. All resolve commands extract ALL issues (not just blocking/should-fix). WONT_FIX added to reports and counts across resolver, resolve.md, resolve-teams.md, and resolve-orchestration. 3. README overhaul: 361→129 lines, story-driven narrative. Detailed content migrated to docs/commands.md, docs/cli-reference.md, docs/working-memory.md, docs/self-learning.md. Stale skill counts fixed across CLAUDE.md and CONTRIBUTING.md.
…nify branches, DRY resolve, README restructure - Remove WONT_FIX category entirely: two outcomes only (FIX or TECH_DEBT) - Evaluate all issues including Suggestions (no longer skipped) - Unify protected branch lists: add integration, trunk across 9 locations - DRY resolve-teams.md batch prompts into reusable template - Add risk protocol summary to resolve.md Phase 4 - README: restore original hook, lead with ambient/TDD/EDD harness, add skill shadowing, literature sources, accurate HUD render, split HUD and security into separate sections Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Three v2 polish improvements in one PR:
implementation-orchestrationnow spawns Git agentsetup-taskon protected branches instead of prompting users. Git agent scans existing remote branches to detect naming conventions (prefix style, separator) before deriving branch names.WONT_FIXfor impractical fixes), systematic 6-step refactoring protocol for careful fixes, and narrowed deferral criteria. All resolve commands/skills now extract ALL issues (not just blocking/should-fix), withWONT_FIXin reports and counts.docs/commands.md,docs/cli-reference.md,docs/working-memory.md,docs/self-learning.md. Stale skill counts fixed across CLAUDE.md and CONTRIBUTING.md.Files Changed (14)
implementation-orchestration/SKILL.md,git.mdresolver.md,resolve-orchestration/SKILL.md,resolve.md,resolve-teams.md,review-methodology/SKILL.mdREADME.md,docs/commands.md,docs/cli-reference.md,docs/working-memory.md,docs/self-learning.md,CONTRIBUTING.md,CLAUDE.mdTest plan
npm run build— distributes updated skills/agents to pluginsnpm test— 578/578 tests passAskUserQuestionin implementation-orchestration